System and method for rideshare vehicle chaining

ABSTRACT

A system to provide instructions to establish a vehicle chain is presented herein. The system includes a memory, controller, and plurality of fleet vehicles. The controller moreover outputs these instructions to at least two vehicles to cause the vehicles to command themselves to establish a vehicle chain to complete a rideshare reservation. As such, a first vehicle may traverse from its vehicle location to a user location and thereafter to a rallying location. Conversely a second vehicle may traverse from its vehicle location to the rallying location and thereafter to a destination location. The controller may output these instructions upon a determination that the vehicles have depleted vehicle resources.

INTRODUCTION

Fleet management systems employed for personal transportation servicescan deploy vehicles made available for reservation. As such, when thesystem has delegated and deployed a vehicle, it will automaticallytraverse itself over to the customer location for pickup. Thereafter,the vehicle will transport/shuttle the customer to their desireddestination and drop the customer off, before repositioning itself forparking or refueling/recharging. Nonetheless, these services can depletesignificant vehicle resources, and make it impracticable for the vehicleto carry out their reservation. Accordingly, it is desirable to providea system and method to instruct deployed fleet vehicles to performreservation tasks in a manner that effectively reduces the issuesassociated with vehicle resource depletion.

SUMMARY

A system to provide instructions to establish a vehicle chain ispresented herein. The system includes a memory, controller, andplurality of fleet vehicles. The memory is configured to include one ormore executable instructions. The controller is configured to executethe executable instructions, the controller is further configured toreceive user location data and destination location data communicatedfrom a mobile computing device. The mobile computing device isconfigured to generate user location data and destination location data,the mobile computing device is further configured to communicate boththe user location data and destination location data to the controller.Each of the fleet vehicles are configured to communicate with thecontroller and each of which has a first vehicle system, second vehiclesystem, and vehicle controls device. The first vehicle system isconfigured to generate vehicle location data, wherein the second vehiclesystem is configured to generate system function data, and wherein thevehicle controls device is configured to command the fleet vehicle toautonomously complete one or more rideshare reservations. Moreover,wherein the executable instructions enable the controller to: receivethe user location data communicated from the mobile computing device;receive the destination location data communicated from the mobilecomputing device; receive the respective vehicle location datacommunicated from each fleet vehicle of the plurality of fleet vehicles;receive the respective system function data communicated from each fleetvehicle of the plurality of fleet vehicles; select at least two fleetvehicles from the plurality of fleet vehicles, wherein each selection isbased, at least in part, on the vehicle location data and systemfunction data of the respective fleet vehicle in relation to the userlocation data (wherein the at least two selected fleet vehicles areconsidered a first-selected vehicle and a second-selected vehicle);produce first output data configured to instruct the vehicle controlsdevice of the first-selected vehicle to command the first-selectedvehicle to traverse from a vehicle location which corresponds to therespective vehicle location data to a user location which corresponds tothe user location data, the first output is further configured tocommand the first-selected vehicle to subsequently traverse from theuser location to a rallying location; produce second output dataconfigured to instruct the vehicle controls device of thesecond-selected vehicle to command the second-selected vehicle totraverse from a vehicle location which corresponds to the respectivevehicle location data to the rallying location, the second output isfurther configured to command the second-selected vehicle tosubsequently traverse from the rallying location to a destinationlocation which corresponds to the destination location data; communicatethe first output data to the first-selected vehicle; and communicate thesecond output data to the second-selected vehicle.

The executable instructions may further enable the controller to selectthe rallying location based, at least in part, on the respective vehiclelocation data and respective system function data of the at least twoselected fleet vehicles. In one or more embodiments, each fleet vehiclein the plurality of fleet vehicles may include a propulsion systemhaving at least one electric motor operatively connected to each of thevehicle wheels. In these embodiments, the second vehicle system is anon-board diagnostic feature and the system function data includes Stateof Charge information. In one or more embodiments, each fleet vehicle inthe plurality of fleet vehicles may include a propulsion system havingat least one internal combustion engine. In these embodiments, thesecond vehicle system is a fuel gauge and the system function dataincludes fuel-level information. The mobile computing device may befurther configured to generate time parameter data and may also befurther configured to communicate the time parameter data to thecontroller, and wherein the selection of the at least two fleet vehiclesfrom the plurality of fleet vehicles is further based, at least in part,on the time parameter data.

A method to provide instructions to establish a vehicle chain is alsopresented herein. The method includes the steps of: providing a memoryconfigured to comprise one or more executable instructions; providing acontroller configured to execute the executable instructions, thecontroller being further configured to receive user location data anddestination location data communicated from a mobile computing device;providing a mobile computing device configured to generate both userlocation data and destination location data, the mobile computing deviceis further configured to communicate the user location data anddestination location data to the controller; providing a plurality offleet vehicles each of which is configured to communicate with thecontroller and each of which comprises a first vehicle system, a secondvehicle system, and a vehicle controls device, wherein the first vehiclesystem is configured to generate vehicle location data, wherein thesecond vehicle system is configured to generate system function data,and wherein the vehicle controls device is configured to command thefleet vehicle to autonomously complete one or more ridesharereservations; receiving (via the controller) the user location datacommunicated from the mobile computing device; receiving (via thecontroller) the destination location data communicated from the mobilecomputing device; receiving (via the controller) the respective vehiclelocation data communicated from each fleet vehicle of the plurality offleet vehicles; receiving (via the controller) the respective systemfunction data communicated from each fleet vehicle of the plurality offleet vehicles; selecting (via the controller) at least two fleetvehicles from the plurality of fleet vehicles, wherein each selection isbased, at least in part, on the vehicle location data and systemfunction data of the respective fleet vehicle in relation to the userlocation data, wherein the at least two selected fleet vehicles areconsidered a first-selected vehicle and a second-selected vehicle;producing (via the controller) first output data configured to instructthe vehicle controls device of the first-selected vehicle to command thefirst-selected vehicle to traverse from a vehicle location whichcorresponds to the respective vehicle location data to a user locationwhich corresponds to the user location data, the first output is furtherconfigured to command the first-selected vehicle to subsequentlytraverse from the user location to a rallying location; producing (viathe controller) second output data configured to instruct the vehiclecontrols device of the second-selected vehicle to command thesecond-selected vehicle to traverse from a vehicle location whichcorresponds to the respective vehicle location data to the rallyinglocation, the second output is further configured to command thesecond-selected vehicle to subsequently traverse from the rallyinglocation to a destination location which corresponds to the destinationlocation data; communicating (via the controller) the first output datato the first-selected vehicle; and communicating (via the controller)the second output data to the second-selected vehicle.

The method may further include the step of selecting (via thecontroller) the rallying location based, at least in part, on therespective vehicle location data and respective system function data ofthe at least two selected fleet vehicles. In one or more embodiments,each fleet vehicle in the plurality of fleet vehicles includes apropulsion system having at least one electric motor operativelyconnected to each of the vehicle wheels. In these embodiments, thesecond vehicle system is an on-board diagnostic feature and the systemfunction data includes State of Charge information. In one or moreembodiments, each fleet vehicle in the plurality of fleet vehiclesincludes a propulsion system having at least one internal combustionengine. In these embodiments, the second vehicle system is a fuel gaugeand the system function data includes fuel-level information. The mobilecomputing device may be further configured to generate time parameterdata and further configured to communicate the time parameter data tothe controller; and thus the step of: selecting (via the controller) theat least two fleet vehicles from the plurality of fleet vehicles isfurther based, at least in part, on the time parameter data.

A non-transitory and machine-readable medium is further presentedherein. The non-transitory and machine-readable medium having storedthereon executable instructions adapted to produce instruction sets forat least two fleet vehicles such that the at least two fleet vehiclesestablish a vehicle chain for the completion of a rideshare reservation,which when provided to a controller and executed thereby, causes thecontroller to: receive user location data communicated from a mobilecomputing device; receive destination location data communicated fromthe mobile computing device; receive respective vehicle location datacommunicated from each fleet vehicle of a plurality of fleet vehicles;receive respective system function data communicated from each fleetvehicle of the plurality of fleet vehicles; select at least two fleetvehicles from the plurality of fleet vehicles, wherein each selection isbased, at least in part, on the vehicle location data and systemfunction data of the respective fleet vehicle in relation to the userlocation data, wherein the at least two selected fleet vehicles areconsidered a first-selected vehicle and a second-selected vehicle;produce first output data configured to instruct the vehicle controlsdevice of the first-selected vehicle to command the first-selectedvehicle to traverse from a vehicle location which corresponds to therespective vehicle location data to a user location which corresponds tothe user location data, the first output is further configured tocommand the first-selected vehicle to subsequently traverse from theuser location to a rallying location; produce second output dataconfigured to instruct the vehicle controls device of thesecond-selected vehicle to command the second-selected vehicle totraverse from a vehicle location which corresponds to the respectivevehicle location data to the rallying location, the second output isfurther configured to command the second-selected vehicle tosubsequently traverse from the rallying location to a destinationlocation which corresponds to the destination location data; communicatethe first output data to the first-selected vehicle; and communicate thesecond output data to the second-selected vehicle. The non-transitoryand machine-readable memory of claim may further include causing thecontroller to select the rallying location based, at least in part, onthe respective vehicle location data and respective system function dataof the at least two selected fleet vehicles.

In one or more embodiments, the non-transitory and machine-readablememory may further cause the controller to: receive time parameter datacommunicated from the mobile computing device, wherein selection of theat least two fleet vehicles from the plurality of fleet vehicles isfurther based, at least in part, on the time parameter data. In one ormore embodiments, each fleet vehicle in the plurality of fleet vehiclesincludes a propulsion system having at least one electric motoroperatively connected to each of the vehicle wheels. In theseembodiments, the second vehicle system is an on-board diagnostic featureand the system function data comprises State of Charge information. Inone or more embodiments, the second vehicle system is a fuel gauge andthe system function data includes fuel-level information.

The above features and advantages and other features and advantages ofthe present teachings are readily apparent from the following detaileddescription for carrying out the teachings when taken in connection withthe accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosed examples will hereinafter be described in conjunction withthe following drawing figures, wherein like numerals denote likeelements, and wherein:

FIG. 1 is a block diagram depicting an exemplary embodiment of acommunications system capable of utilizing the system and methoddisclosed herein;

FIG. 2 is a schematic diagram of an autonomously controlled electricvehicle, according to an embodiment of the communications system of FIG.1;

FIG. 3 is a schematic block diagram of an exemplary automated drivingsystem (ADS) for the vehicle of FIG. 2; and

FIG. 4 represents a flow chart for an exemplary methodology for vehiclechaining as disclosed herein;

FIG. 5 represents an exemplary map illustrating aspects of the systemand method disclosed herein; and

FIG. 6 further represents exemplary aspects of the method and systemdisclosed herein.

DETAILED DESCRIPTION

Embodiments of the present disclosure are described herein. It is to beunderstood, however, that the disclosed embodiments are merely examplesand other embodiments can take various and alternative forms. Thefigures are not necessarily to scale; some features could be exaggeratedor minimized to show details of particular components. Therefore,specific structural and functional details disclosed herein are not tobe interpreted as limiting, but merely as a representative basis forteaching one skilled in the art to variously employ the present systemand/or method. As those of ordinary skill in the art will understand,various features illustrated and described with reference to any one ofthe figures can be combined with features illustrated in one or moreother figures to produce embodiments that are not explicitly illustratedor described. The combinations of features illustrated providerepresentative embodiments for typical applications. Variouscombinations and modifications of the features consistent with theteachings of this disclosure, however, could be desired for particularapplications or implementations.

The following detailed description is merely exemplary in nature and isnot intended to limit the application and uses. Furthermore, there is nointention to be bound by any expressed or implied theory presented inthe preceding background and brief summary or the following detaileddescription. As used herein, the term module refers to an applicationspecific integrated circuit (ASIC), an electronic circuit, a processor(shared, dedicated, or group) and memory that executes one or moresoftware or firmware programs or code segments, a combinational logiccircuit, and/or other suitable components that provide the describedfunctionality.

As shown in FIG. 1, there is shown a non-limiting example of acommunication system 10 that may be used together with examples of thesystem disclosed herein and/or to implement examples of the methodsdisclosed herein. Communication system 10 generally includes a fleet ofvehicles 12 (shown as one), a wireless carrier system 14, a land network16, and a data center 18 (i.e., the backend). It should be appreciatedthat the overall architecture, setup and operation, as well as theindividual components of the illustrated system are merely exemplary andthat differently configured communication systems may also be utilizedto implement the examples of the system and/or method disclosed herein.Thus, the following paragraphs, which provide a brief overview of theillustrated communication system 10, are not intended to be limiting.

Each fleet vehicle 12 may be any type of user operated or autonomousvehicle (discussed below) such as a motorcycle, car, truck, bicycle,recreational vehicle (RV), boat, plane, etc., and is equipped withsuitable hardware and software that enables it to communicate overcommunication system 10. Vehicle 12 may include a power train systemwith multiple generally known torque-generating devices including, forexample, an engine 13. In certain embodiments, engine 13 can be aninternal combustion engine that uses one or more cylinders to combustfuel, such as gasoline, in order to propel vehicle 12. In one or morealternative embodiments, however, the power train system can includenumerous electric motors or traction motors that convert electricalenergy into mechanical energy for propulsion of vehicle 12 (discussedbelow). Skilled artists will also see engine 13 can be acompression-ignition engine which uses a combustion chamber to combustfuel, such as diesel fuel, compressed natural gas, or propane.

Some of the fundamental vehicle hardware 20 for each fleet vehicle isshown generally in FIG. 1 including a telematics unit 24, a microphone26, speaker 28, and buttons and/or controls 30 connected to telematicsunit 24. Operatively coupled to telematics unit 24 is a networkconnection or vehicle bus 32. Examples of suitable network connectionsinclude a controller area network (CAN), a media oriented systemtransfer (MOST), a local interconnection network (LIN), an Ethernet,dedicated short-range communications channel (DSRC), and otherappropriate connections such as those that conform with known ISO(International Organization for Standardization), SAE (Society ofAutomotive Engineers), and/or IEEE (Institute of Electrical andElectronics Engineers) standards and specifications, to name a few.

The telematics unit 24 is a communication system which provides avariety of services through its communications with the data center 18,and generally includes an electronic processing device 38, one or moretypes of electronic memory 40, a cellular chipset/component 34, wirelessmodem 36, dual mode antenna 70, and navigation unit containing a GPSchipset/component 42 capable of communicating vehicle locationinformation via a GPS satellite system 65. GPS component 42 thusreceives coordinate signals from a constellation of GPS satellites 65.From these signals, the GPS component 42 can determine vehicle position,which may be used for providing navigation and other position-relatedservices to the vehicle operator. Navigation information can bepresented on a display of telematics unit 24 (or other display withinthe vehicle) or can be presented verbally such as is done when supplyingturn-by-turn navigation. The navigation services can be provided using adedicated in-vehicle navigation module (which can be part of GPScomponent 42), or some or all navigation services can be done viatelematics unit 24, wherein the location coordinate information (vehiclelocation data) is sent to a remote location for purposes of providingthe vehicle with navigation maps, map annotations, route calculations,and the like.

The telematics unit 24 may provide various services including:turn-by-turn directions and other navigation-related services providedin conjunction with the GPS component 42; airbag deployment notificationand other emergency or roadside assistance-related services provided inconnection with various crash and/or collision sensor interface modules66 and collision sensors 68 located throughout the vehicle and/orinfotainment-related services where music, internet web pages, movies,television programs, videogames, and/or other content are downloaded byan infotainment center 46 operatively connected to the telematics unit24 via vehicle bus 32 and audio bus 22. In one example, downloadedcontent is stored for current or later playback. The above-listedservices are by no means an exhaustive list of all the capabilities oftelematics unit 24, but are simply an illustration of some of theservices telematics unit 24 may be capable of offering. It isanticipated that telematics unit 24 may include a number of additionalcomponents in addition to and/or different components from those listedabove.

Vehicle communications may use radio transmissions to establish a voicechannel with wireless carrier system 14 so that both voice and datatransmissions can be sent and received over the voice channel. Vehiclecommunications are enabled via the cellular component 34 for voicecommunications and the wireless modem 36 for data transmission. Anysuitable encoding or modulation technique may be used with the presentexamples, including digital transmission technologies, such as TDMA(time division multiple access), CDMA (code division multiple access),W-CDMA (wideband CDMA), FDMA (frequency division multiple access), OFDMA(orthogonal frequency division multiple access), etc. To accomplish thiseffect, dual mode antenna 70 services the GPS component 42 and thecellular component 34.

Microphone 26 provides the driver or other vehicle occupant with a meansfor inputting verbal or other auditory commands, and can be equippedwith an embedded voice processing unit utilizing a human/machineinterface (HMI) technology known in the art. Conversely, speaker 28provides audible output to the vehicle occupants and can be either astand-alone speaker specifically dedicated for use with the telematicsunit 24 or can be part of a vehicle audio component 64. In either event,microphone 26 and speaker 28 enable vehicle hardware 20 and data center18 to communicate with the occupants through audible speech. The vehiclehardware also includes one or more buttons and/or controls 30 forenabling a vehicle occupant to activate or engage one or more of thevehicle hardware components 20. For example, one of the buttons and/orcontrols 30 can be an electronic pushbutton used to initiate voicecommunication with data center 18 (whether it be a human such as advisor58 or an automated call response system). In another example, one of thebuttons and/or controls 30 can be used to initiate emergency services.

The audio component 64 is operatively connected to the vehicle bus 32and the audio bus 22. The audio component 64 receives analoginformation, rendering it as sound, via the audio bus 22. Digitalinformation is received via the vehicle bus 32. The audio component 64provides amplitude modulated (AM) and frequency modulated (FM) radio,compact disc (CD), digital video disc (DVD), and multimediafunctionality independent of the infotainment center 46. Audio component64 may contain a speaker system, or may utilize speaker 28 viaarbitration on vehicle bus 32 and/or audio bus 22.

The vehicle crash and/or collision detection sensor interface 66 isoperatively connected to the vehicle bus 32. The collision sensors 68provide information to telematics unit 24 via the crash and/or collisiondetection sensor interface 66 regarding the severity of a vehiclecollision, such as the angle of impact and the amount of forcesustained.

Vehicle sensors 72, connected to various vehicle sensor modules 44(VSMs) in the form of electronic hardware components located throughouteach fleet vehicle and use the sensed input to perform diagnostic,monitoring, control, reporting and/or other functions. Each of the VSMs44 is preferably connected by vehicle bus 32 to other VSMs 44, as wellas to telematics unit 24, and can be programmed to run vehicle systemand subsystem diagnostic tests. As examples, one VSM 44 can be an enginecontrol module (ECM) that controls various aspects of engine operationsuch as fuel ignition and ignition timing. According to one embodiment,the ECM is equipped with on-board diagnostic (OBD) feature that providesmyriad real-time system function data, such as that received fromvarious sensors including vehicle emissions sensors, fuel diagnosticssensors, and vehicle oil pressure sensors as well as provide astandardized series of diagnostic trouble codes (DTCs) which allow atechnician to rapidly identify and remedy malfunctions within thevehicle. VSM 44 can similarly be a powertrain control module (PCM) thatregulates operation of one or more components of the powertrain system.According to one embodiment, the PCM is equipped with a fuel gaugelocated in the fuel tank 67 and which provides fuel-level information toindicate the amount of fuel contained in fuel tank 67. Another VSM 44can be a body control module (BCM) that monitors and governs variouselectrical components located throughout the vehicle body like thevehicle's power door locks, air conditioner, tire pressure, lightingsystem, engine ignition, vehicle seat adjustment and heating, mirrors,and headlights. Furthermore, as can be appreciated by skilled artisans,the above-mentioned VSMs are only examples of some of the modules thatmay be used the vehicles 12, as numerous others are also possible.

A passive entry passive start (PEPS) module, for instance, is another ofthe numerous of VSMs and provides passive detection of the absence orpresence of a passive physical key or a virtual vehicle key. When thepassive physical key approaches, the PEPS module can determine if thepassive physical key is authentic as belonging to the vehicle. The PEPScan likewise use authentication information received from data center 18to determine if a mobile computing device 57 with virtual vehicle key isauthorized/authentic to vehicle. When the virtual vehicle key is deemedauthentic, the PEPS can send a command to BCM 44 permitting access toits vehicle. It should be understood that the PEPS may be an electronichardware component connected to the vehicle bus 32 or, in an alternativeembodiment, may be one or more software code segments uploaded toelectronic memory 40.

Wireless carrier system 14 may be a cellular telephone system or anyother suitable wireless system that transmits signals between thevehicle hardware 20 and land network 16. According to an example,wireless carrier system 14 includes one or more cell towers 48.

Land network 16 can be a conventional land-based telecommunicationsnetwork connected to one or more landline telephones, and that connectswireless carrier system 14 to data center 18. For example, land network16 can include a public switched telephone network (PSTN) and/or anInternet protocol (IP) network, as is appreciated by those skilled inthe art. Of course, one or more segments of the land network 16 can beimplemented in the form of a standard wired network, a fiber or otheroptical network, a cable network, other wireless networks such aswireless local networks (WLANs) or networks providing broadband wirelessaccess (BWA), or any combination thereof.

As revealed above, one of the networked devices that can directly orindirectly communicate with the telematics unit 24 is a mobile computingdevice 57, such as (but not limited to) a smart phone, personal laptopcomputer or tablet computer having two-way communication capabilities, awearable computer such as (but not limited to) a smart watch or glasses,or any suitable combinations thereof. The mobile computing device 57 caninclude computer processing capability, a transceiver 53 capable ofcommunicating with remote locations (e.g., data center 18), digitalcamera 55, user interface 59, and/or GPS module 63 capable of receivingGPS satellite signals and generating GPS coordinates based on thosesignals. User interface 59 may be embodied as a touch-screen graphicalinterface capable of user interaction as well as exhibiting information.Digital camera 55 may include the ability to generate bitmapped datarepresentations of captured tangible-object images through generallyknown operations. Examples of the mobile computing device 57 include theiPhone™ and Apple Watch™ each being manufactured by Apple, Inc. and theDroid™ smart phone manufactured by Motorola, Inc. as well as others.

Mobile device 57 may be used inside or outside of a vehicle, and may becoupled to the vehicle by wire or wirelessly. Mobile device 57 may alsobe configured to provide services according to a subscription agreementwith a third-party facility or wireless/telephone service provider. Itshould be appreciated that various service providers may utilize thewireless carrier system 14 and that the service provider of telematicsunit 30 may not necessarily be the same as the service provider ofmobile device 57.

When using a short-range wireless connection (SRWC) protocol (e.g.,Bluetooth Low Energy, Wi-Fi, etc.), mobile computing device 57 andtelematics unit 24 may pair with each other (or link to one another) ona case-by-case basis and while within a wireless range; SRWC pairing isknown to skilled artisans. The SRWC protocol may be an aspect oftelematics unit 24 or may be part of one or more independent VSMs 44such as the PEPS and/or BCM 44. Once SRWC is established, the devicesmay be considered bonded (i.e., they may recognize one another and/orconnect automatically when they are in a predetermined proximity orrange of one other. In other words—they may become, at leasttemporarily, network participants).

This unique pairing, for example, allows mobile computing device 57 toact as the virtual key fob briefly mentioned above. To illustrate howvirtual key fob pairing can occur—upon receiving a request, data center18 will generate an encrypted virtual vehicle key to permit vehicleaccess via mobile computing device 57. Data center 18 will then transmitaspects of this encrypted virtual vehicle key information to both mobilecomputing device 57 and the PEPS module 44 via telematics unit 24. Afterpairing has been established, mobile computing device 57 will send itsvirtual vehicle key aspect to telematics unit 24 for recognition inlight of its stored corresponding virtual key aspect and in turn thePEPS may establish mobile computing device 57 as the acting key fob forthe vehicle. Data center 18 may also transmit one or more timeparameters with the encrypted virtual vehicle key information so as totemporarily establish the virtual vehicle key of mobile device 57.

Data center 18 is designed to provide the vehicle hardware 20 with anumber of different system backend functions and, according to theexample shown here, generally includes one or more switches 52, servers54, databases 56, advisors 58 as well as a variety of othertelecommunication/computer equipment 60. These various data centercomponents are suitably coupled to one another via a network connectionor bus 62, such as the one previously described in connection with thevehicle hardware 20. Switch 52, which can be a private branch exchange(PBX) switch, routes incoming signals so that voice transmissions areusually sent to either advisor 58 or an automated response system, anddata transmissions are passed on to a modem or other piece oftelecommunication/computer equipment 60 for demodulation and furthersignal processing. The modem or other telecommunication/computerequipment 60 may include an encoder, as previously explained, and can beconnected to various devices such as a server 54 and database 56.Although the illustrated example has been described as it would be usedin conjunction with a manned data center 18, it will be appreciated thatthe data center 18 can be any central or remote facility, manned orunmanned, mobile or fixed, to or from which it is desirable to exchangevoice and data.

Server 54 can incorporate a data controller which essentially controlsits operations. Server 54 may control data information as well as act asa transceiver to send and/or receive the data information (i.e., datatransmissions) from one or more of the databases 54, telematics unit 24,and mobile computing device 57. The controller is moreover capable ofreading executable instructions stored in a non-transitory machinereadable medium and may include one or more from among a processor,microprocessor, central processing unit (CPU), graphics processor,Application Specific Integrated Circuits (ASICs), Field-ProgrammableGate Arrays (FPGAs), state machines, and a combination of hardware,software, and firmware components.

Database 56 could be designed to store information in the form ofexecutable instructions such as, but not limited to, numerousapplication program interface (API) suites. Moreover, in certaininstances, these API suites may be accessible to the system user, datacenter 18, or one or more third parties. As examples, one API suite canbe a rideshare services suite that incorporates numerous ridesharesystem records (i.e., vehicle reservation information) each havinginformation related to the vehicles in fleet 12 such as, but not limitedto, rideshare vehicle records (e.g., vehicle VSM information),information related to the user such as, but not limited to, reservationaccount records (e.g., vehicle comfort settings information, telematicsunit settings, or vehicle make-model preferences), information relatedto organizing vehicle reservations such as, but not limited to,reservation profile records (e.g., reservation calendar information,vehicle assignment information, third party contact information, etc.),and information related to fleet management (e.g., fleet vehiclefeedback data, localization and mapping data, path planning feedbackdata, etc.), or any other pertinent rideshare system information. Therecords can moreover be copied, organized, and/or stored in a tabularform that allows for continuous, real-time updates. The records canadditionally collaborate with a reservation account (discussed below)for support of, for example, reservation management.

The user of mobile computing device 57 may create their own personalizedvehicle reservation account to be stored in mobile memory 61 and whichmay have access to the rideshare records at the backend. The user mayperform tasks to create this account through a variety of frontenddevices such as, for example, through a remote computer and mobilecomputing device 57. This reservation account may be uploaded to oraccessible on server 54 (i.e., to support backend functions). Datacenter 20 may also access one or more additional remote servers and/orremote databases (e.g., Department of Motor Vehicles, weather databases,traffic databases, etc.) to receive information in support ofestablishing the reservation account as well as a particular reservationand one or more rideshare system records.

The reservation account may include validating data to verify and/orvalidate that future login attempts are secure (e.g., granting accessonly to the user). The validating data may include an account usernameand account password as well as user information (e.g., driver's licenseinformation), mobile computing device information such as, for example,the unique mobile device identifier (i.e., serial number). The useraccount may additionally store a variety of user preferences.

The user of mobile device 57 may visit an online software applicationstore or web-service and download the reservation account as a softwaremodule therefrom. The reservation account may moreover include one ormore prompts to instruct the user to provide information (e.g.,validating data) to support account creation.

Reservation account may also provide one or more prompts to assist arideshare system user in reserving a personal transportation fleetvehicle by operatively accessing and communicating with the backendrideshare system records (for the purposes of obtaining transportationto certain destinations). Once a reservation is made, mobile computingdevice 57 will transmit this reservation information to one or more ofthe rideshare records for updates thereto. At the backend, server 54will collaborate with database 56 and one or more of the ridesharesystem records to establish a subset of the fleet available forreservation.

To illustrate, for example, server 54 can manage the use of a fleet oftwenty (20) vehicles in a particular geographic location and determinethat ten (10) of those vehicles are available to carry out the requestedrideshare reservation. Server 54 will then, for example, select one ofthose fleet vehicles using a vehicle identifier and assign thatidentifier to the reservation account and corresponding ridesharerecords for use during the requested reservation. Server 54 thencommunicates provided pickup coordinates and drop off coordinates to theselected fleet vehicle via its telematics unit 24 so the vehicle candirect itself to the user, pick the user up, and then drop the user offat a designated location. As vehicles are requested and used, server 54can determine the identities of the vehicles currently in use andmonitor various aspects of the other fleet vehicles so as to understandwhich vehicles are available at any particular time. This monitoringprocess may thus be conducted through review of one or more ridesharerecords.

In another example, when vehicle resources are scarce and time may be afactor, server 54 can determine that the requested reservation includesreservation information that indicates the distance between the pickupcoordinates and drop off coordinates is beyond the remaining distanceallowed for any one available vehicle. As a result, based on thesefactors, server 54 will select two of those available fleet vehicles tocarry out the requested reservation using a vehicle identifier for bothvehicles and assign that identifier to the reservation account andcorresponding rideshare records. Server 54 then communicates both thepickup coordinates and coordinates of a rallying location to thetelematics unit of one selected fleet vehicle so this first vehicle candirect itself to the user for pickup. Server 54 also communicates therallying location coordinates and drop off coordinates to the otherselected fleet vehicle so this second vehicle can direct itself to therallying location and wait for the first vehicle to arrive. In this way,the selected vehicles are considered to create a vehicle chain and theuser can switch vehicles midway through their reservation. Skilledartists will see that server 54 can select more than two of theavailable vehicles to work in concert to complete a ridesharereservation. Skilled artists will further see that each vehicle'sremaining allowable distance may be determined by the remaining SoC forthe power source as indicated by OBD 44 or, in the alternative, may bedetermined by the remaining fuel as indicated by fuel gauge 44. Therallying location coordinates may moreover be based upon the allowablevehicle distances.

Electric Vehicle Aspects

With reference to FIG. 2, each fleet vehicle 12 can be embodied as anelectric vehicle (EV) that generally includes vehicle wheels 215 whichrotatably support a vehicle body 211. Fleet vehicle 12 further includesa propulsion system 213 with at least one electric motor 219. Anelectric motor 219 is operatively connected to each of the vehiclewheels 215 to transmit torque thereto, and thereby propel the fleetvehicle 12. These motors may moreover, in one or more embodiments, bedirectly or indirectly connected to their corresponding wheel via atransmission 214 (shown as a direct connection configuration). It shouldbe understood that the fleet vehicles may also be embodied as anextended range electric vehicle (EREV) or hybrid vehicle (combining aninternal combustion engine with one or more electric motors).

Propulsion system 213 can also include a power source 218 embodied as abattery for the purpose of providing direct-current (DC) electricity topower each of the motors, as well as other vehicle systems. Each motormay be a permanent-magnet motor, induction motor, or any type of motorthat uses alternating current (AC) electricity. Consequently, propulsionsystem 213 can include an inverter aspect 220 operatively connected tothe power source output so as to allow the DC current to be convertedinto AC current before being supplied to the motors. Propulsion system213 may additionally be connected to a vehicle controls device 222,discussed below, to regulate the amount of transmitted energy from powersource 218 so as to effectively control the torque output from eachmotor 219. Propulsion system 213 may further include an input component,which in some embodiments can be operable by a human (i.e., aselectively depressible foot pedal), to provide for an input of adesired torque output. Propulsion system 213 may moreover be connectedto vehicle bus 32 to communicate with one or more VSMs 44 (not shown).For example, OBD 44 may provide State of Charge (SoC) information forpower source 218 based on information received from one or more powerreading sensors.

While depicted as a single unit for illustrative purposes, vehiclecontrols device 222 may additionally include one or more othercontrollers, collectively referred to as a “controls device” or “vehiclecontrols device.” Controls device 222 may include a microprocessor suchas a central processing unit (CPU) or graphics processing unit (GPU) incommunication with various types of computer readable storage devices ormedia. Computer readable storage devices or media may include volatileand nonvolatile storage in read-only memory (ROM), random-access memory(RAM), and keep-alive memory (KAM), for example. KAM is a persistent ornon-volatile memory that may be used to store various operatingvariables while the CPU is powered down. Computer-readable storagedevices or media may be implemented using any of a number of knownmemory devices such as PROMs (programmable read-only memory), EPROMs(electrically PROM), EEPROMs (electrically erasable PROM), flash memory,or any other electric, magnetic, optical, or combination memory devicescapable of storing data, some of which represent executableinstructions, used by the controls device 222 in controlling thevehicle.

Autonomous Vehicle Aspects

In addition to the fleet vehicle aspects discussed above, transmission214 may be installed to transmit power from propulsion system 213 tovehicle wheels 215 according to selectable speed ratios. According tovarious embodiments, transmission 214 may include a step-ratio automatictransmission, a continuously-variable transmission, or other appropriatetransmission. Fleet vehicle 12 additionally includes wheel brakes 217configured to provide braking torque to the vehicle wheels 215. Thewheel brakes 217 may, in various embodiments, include friction brakes, aregenerative braking system such as an electric machine, and/or otherappropriate braking systems. It should be understood transmission 214does not necessarily need to be installed for propulsion system 213 topropel fleet vehicle 12.

Each fleet vehicle 12 additionally includes a steering system 216. Whiledepicted as including a steering wheel for illustrative purposes, insome contemplated embodiments, the steering system 16 may not include asteering wheel. Telematics unit 24 is additionally configured towirelessly communicate with other vehicles (“V2V”) and/or infrastructure(“V2I”) and/or pedestrians (“V2P”). These communications maycollectively be referred to as a vehicle-to-entity communication(“V2X”). In an exemplary embodiment, this communication systemcommunicates via at least one dedicated short-range communications(DSRC) channel. DSRC channels refer to one-way or two-way short-range tomedium-range wireless communication channels specifically designed forautomotive use and a corresponding set of protocols and standards.

The propulsion system 213 (explained above), transmission 214, steeringsystem 216, and wheel brakes 217 are in communication with or undercontrols device 222. Vehicle controls device 222 includes an automateddriving system (ADS) 224 for automatically controlling various actuatorsin the vehicle. In an exemplary embodiment, ADS 224 is a so-called LevelFour or Level Five automation system. A Level Four system indicates“high automation”, referring to the driving mode-specific performance byan automated driving system of all aspects of the dynamic driving task,even if a human driver does not respond appropriately to a request tointervene. A Level Five system indicates “full automation”, referring tothe full-time performance by an automated driving system of all aspectsof the dynamic driving task under all roadway and environmentalconditions that can be managed by a human driver. In an exemplaryembodiment, the ADS 224 is configured to communicate automated drivinginformation with and control propulsion system 213, transmission 214,motors 219, steering system 216, and wheel brakes 217 to control vehicleacceleration, steering, and braking, respectively, without humanintervention via a plurality of actuators 30 in response to inputs froma plurality of driving sensors 226, which may include GPS, RADAR, LIDAR,optical cameras, thermal cameras, ultrasonic sensors, and/or additionalsensors as appropriate.

In various embodiments, the instructions of the ADS 224 may be organizedby function or system. For example, as shown in FIG. 3, ADS 224 caninclude a sensor fusion system 232 (computer vision system), apositioning system 234, a guidance system 236, and a vehicle controlsystem 238. As can be appreciated, in various embodiments, theinstructions may be organized into any number of systems (e.g.,combined, further partitioned, etc.) as the disclosure is not limited tothe present examples.

In various embodiments, the sensor fusion system 232 synthesizes andprocesses sensor data and predicts the presence, location,classification, and/or path of objects and features of the environmentof the vehicle 12. In various embodiments, the sensor fusion system 232can incorporate information from multiple sensors, including but notlimited to cameras, lidars, radars, and/or any number of other types ofsensors. In one or more exemplary embodiments described herein, thesensor fusion system 232 supports or otherwise performs the groundreference determination processes and correlates image data to lidarpoint cloud data, the vehicle reference frame, or some other referencecoordinate frame using calibrated conversion parameter values associatedwith the pairing of the respective camera and reference frame to relatelidar points to pixel locations, assign depths to the image data,identify objects in one or more of the image data and the lidar data, orotherwise synthesize associated image data and lidar data. In otherwords, the sensor output from the sensor fusion system 232 provided tothe vehicle control system 238 (e.g., indicia of detected objects and/ortheir locations relative to the vehicle 10) reflects or is otherwiseinfluenced by the calibrations and associations between camera images,lidar point cloud data, and the like.

The positioning system 234 processes sensor data along with other datato determine a position (e.g., a local position relative to a map, anexact position relative to lane of a road, vehicle heading, velocity,etc.) of the vehicle 12 relative to the environment. The guidance system236 processes sensor data along with other data to determine a path forthe vehicle 12 to follow (i.e., path planning data). The vehicle controlsystem 238 generates control signals for controlling the vehicle 12according to the determined path.

In various embodiments, the vehicle controls device 222 implementsmachine learning techniques to assist the functionality of the vehiclecontrols device 222, such as feature detection/classification,obstruction mitigation, route traversal, mapping, sensor integration,ground-truth determination, and the like.

The output of vehicle controls device 222 is communicated to actuators230. In an exemplary embodiment, the actuators 230 include a steeringcontrol, a shifter control, a throttle control, and a brake control. Thesteering control may, for example, control a steering system 216 asillustrated in FIG. 2. The shifter control may, for example, control atransmission 214 as illustrated in FIG. 2. The throttle control may, forexample, control a propulsion system 213 as illustrated in FIG. 2. Thebrake control may, for example, control wheel brakes 217 as illustratedin FIG. 2.

Method

As explained above, at least partially, rideshare systems are thosesystems which allows a user (rideshare system user) to download areservation account to a mobile computing device and then register theiraccount by providing personal and/or payment information. The user maythen have access to a rideshare system to request personaltransportation from an available autonomous vehicle (discussed above),generally within a certain proximity of their location or a selectedlocation (e.g., 5-10 miles) and able to meet desired reservation timerestrictions. During the rideshare reservation, a delegated vehicle willautonomously traverse to the user's location, pick the user up,autonomously transport the user to their selected destination to dropthe user off before their deadline. Afterwards, the user may be providedan opportunity to submit their own feedback/rating of one or more of therideshare system services. The vehicle may moreover autonomouslytraverse to the next request, a parking location, or a vehicle chargestation or refueling station.

Nevertheless, a user may request transportation which, if carried out asdiscussed in the preceding paragraph, would exceed the allowable vehicleresources of any available vehicle. Moreover, there may not be enoughtime for any one of the available vehicles to replenish resources beforethe reservation's established time limit. Under such circumstances, therideshare system can delegate one vehicle to autonomously traverse tothe user's location, pick the user up, and transport the user to arallying point. A second system delegated vehicle can then pick the userup at this rallying point and transport the user to the selecteddestination location before the reservation deadline.

Turning now to FIG. 4, to detail the circumstances above, there can beseen an application of a method to produce instruction sets for at leasttwo delegated fleet vehicles so as to work in concert to complete arideshare reservation. Aspects of this method may be executed throughserver 54, for example, implementing the backend functionality stored ondatabase 56. Peripheral aspects may be executed through controls device222 of each delegated fleet vehicle 12, for example, to implement thegenerated instructions and cause the fleet vehicle to properly traversethe generated route presented in their respective instruction set.

Upon initiation 401, a user will be prompted to provide their desireduser pickup location as well as their desired drop off destinationlocation via their reservation account, for example, on their mobiledevice 57. The user location may be the GPS coordinates of mobilecomputing device 57 or this location may be designated by the userthrough one or more reservation account prompts. The user may also beprompted to provide a specified time parameter which establishes thereservation deadline. For example, the user may communicate to theirreservation account they desire to be picked up at their currentlocation and dropped off at some distant location (e.g., their homelocated 10 miles away). The user may also communicate that they wouldlike to be dropped off at this distant location within an hour.

In step 410, the reservation process begins, at least in part, whenserver 54 receives the user location data from the remotely locatedmobile computing device 57. Server 54 will then determine the userlocation corresponding to this data and filter and format thesecoordinates in a suitable form. This may be done via, for example whenthe user location data are embodied as GPS coordinates, a known locationinterface module stored in databases 56. This may otherwise be done via,for example when the user location data is designated by the user viathe reservation account, a known map data module stored in databases 56.In this step, optionally, server may also receive time parameter datacorresponding to the user location data. For example, the time parameterdata of this step may establish the delegated fleet vehicle is to be atthe user location no later than fifteen (15) minutes from thereservation being established.

In step 420, server 54 will similarly receive the destination locationdata from the remotely located mobile computing device 57. Server 54will then determine the destination location corresponding to this dataand filter and format these coordinates in a suitable form. This may bedone via, for example, the map data module. In this step, optionally,server 54 may also receive time parameter data corresponding to thedestination location data. For example, the time parameter data mayestablish the delegated fleet vehicle is to be at the destinationlocation no later than one (1) hour from departing the user location.

In step 430, server 54 will conduct a census of any/all fleet vehicleslast known to be within a certain proximity of the designated userlocation. For example, server 54 may request and receive GPS data fromthe available fleet vehicles last known to be within five (5) miles fromthe user location. Upon census completion, server 54 will determine thevehicle location coordinates for each of these fleet vehicles.

In step 440, server 54 will request and receive the system function datafor the vehicles determined within proximity of the user locationcoordinates. When the fleet vehicles are embodied as electric vehicles,discussed above, incorporating numerous electric motors, the systemfunction data can be State of Charge information sensed from thevehicle's on-board diagnostic feature (OBD) 44. When the fleet vehiclesincorporate a propulsion system with an internal combustion engine, onthe other hand, the system function data can be fuel-level informationsensed from the vehicle's fuel gauge 44.

In this step, furthermore, server 54 will determine if any of thesevehicles have/will have enough resources (i.e., State of Charge/fuel) tosafely carryout the reservation as requested (i.e., carryout thereservation tasks and still have enough remaining resources to arrive ata charge/fuel station). If one or more of the fleet vehicles is able tocarryout the reservation, one of those vehicles will be delegated tocarryout the reservation and method 400 will move to completion 402.However, if it is determined that none of the vehicles have/will haveenough resources, method 400 will move to step 450.

In step 450, with reference to FIGS. 5 and 6, server 54 will review andanalyze the system function data of each vehicle in light of theirrespective vehicle locations 506 and 510, the user location 502, and thedestination location 504. Thereafter, server 54 will select at least twovehicles based on these factors. For instance, the fleet vehicle atvehicle location 506 has an estimated travel range 508 which can onlyallow the vehicle to get part way to the destination location 504 aftergetting the user at their user location 508. Conversely, the fleetvehicle at vehicle location 510 has an estimated travel range 512 whichdoes not allow the vehicle to reach the user location 508 but allows thevehicle to reach destination location 504. Therefore, server 54 mayselect the vehicles at location 506 and the vehicle at location 510because each is unable to carry out the reservation by themselves butcan carry out the entire reservation when working in concert. Factoringinto account the remaining vehicle resources, server 54 will also createa rallying location 514 located somewhere between the two vehiclelocations 506 and 510. The rallying point location 514 acts as a midwaypoint in which the selected vehicles are to meet (i.e., to establish avehicle chain).

In step 460, server 54 will produce a set of instructions (i.e., outputdata) formatted to instruct the vehicle controls device 222 of firstvehicle 12 a to command the vehicle to traverse from its respectivevehicle location 506 to the user location 508. Upon user pickup, theinstructions will instruct vehicle controls device 222 to command thefirst vehicle 12 a to traverse to rallying point 514. In step 470,server 54 will communicate these instructions as a first output to thefirst vehicle 12 a to be received by vehicle controls device 222.

In step 480, likewise, server 54 will produce a set of instructionsformatted to instruct the vehicle controls device 222 of the secondvehicle 12 b to command the vehicle to traverse from its respectivevehicle location 510 to rallying point 514 to wait for the first vehicle12 a. Upon arrival, the instructions will instruct vehicle controlsdevice 222 to command the second vehicle 12 b to take the user fromrallying point 514 to destination location 504. In step 490, server 54will communicate these instructions as a second output to the secondvehicle 12 b to be received by the corresponding vehicle controls device222. Once both outputs, the first and second output, have beenadequately communicated, method 400 will move to completion 402.

The processes, methods, or algorithms disclosed herein can bedeliverable to/implemented by a processing device, controller, orcomputer, which can include any existing programmable electronic controlunit or dedicated electronic control unit. Similarly, the processes,methods, or algorithms can be stored as data and instructions executableby a controller or computer in many forms including, but not limited to,information permanently stored on non-writable storage media such as ROMdevices and information alterably stored on writeable storage media suchas floppy disks, magnetic tapes, CDs, RAM devices, and other magneticand optical media. The processes, methods, or algorithms can also beimplemented in a software executable object. Alternatively, theprocesses, methods, or algorithms can be embodied in whole or in partusing suitable hardware components, such as Application SpecificIntegrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGAs),state machines, controllers or other hardware components or devices, ora combination of hardware, software and firmware components.

While exemplary embodiments are described above, it is not intended thatthese embodiments describe all possible forms encompassed by the claims.The words used in the specification are words of description rather thanlimitation, and it is understood that various changes can be madewithout departing from the spirit and scope of the disclosure. Aspreviously described, the features of various embodiments can becombined to form further embodiments of the system and/or method thatmay not be explicitly described or illustrated. While variousembodiments could have been described as providing advantages or beingpreferred over other embodiments or prior art implementations withrespect to one or more desired characteristics, those of ordinary skillin the art recognize that one or more features or characteristics can becompromised to achieve desired overall system attributes, which dependon the specific application and implementation. These attributes caninclude, but are not limited to cost, strength, durability, life cyclecost, marketability, appearance, packaging, size, serviceability,weight, manufacturability, ease of assembly, etc. As such, embodimentsdescribed as less desirable than other embodiments or prior artimplementations with respect to one or more characteristics are notoutside the scope of the disclosure and can be desirable for particularapplications.

What is claimed is:
 1. A system to provide instructions to establish avehicle chain, the system comprises: a memory configured to comprise oneor more executable instructions; a controller configured to execute theexecutable instructions, the controller further configured to receiveuser location data and destination location data communicated from amobile computing device; a plurality of fleet vehicles each of which isconfigured to communicate with the controller and each of whichcomprises a first vehicle system, a second vehicle system, and a vehiclecontrols device; wherein the first vehicle system is configured togenerate vehicle location data, wherein the second vehicle system isconfigured to generate system function data, and wherein the vehiclecontrols device is configured to command the fleet vehicle toautonomously complete one or more rideshare reservations; and whereinthe executable instructions enable the controller to: receive the userlocation data communicated from the mobile computing device; receive thedestination location data communicated from the mobile computing device;receive the respective vehicle location data communicated from eachfleet vehicle of the plurality of fleet vehicles; receive the respectivesystem function data communicated from each fleet vehicle of theplurality of fleet vehicles; select at least two fleet vehicles from theplurality of fleet vehicles, wherein each selection is based, at leastin part, on the vehicle location data and system function data of therespective fleet vehicle in relation to the user location data, whereinthe at least two selected fleet vehicles are considered a first-selectedvehicle and a second-selected vehicle; produce first output dataconfigured to instruct the vehicle controls device of the first-selectedvehicle to command the first-selected vehicle to traverse from a vehiclelocation which corresponds to the respective vehicle location data to auser location which corresponds to the user location data, the firstoutput is further configured to command the first-selected vehicle tosubsequently traverse from the user location to a rallying location;produce second output data configured to instruct the vehicle controlsdevice of the second-selected vehicle to command the second-selectedvehicle to traverse from a vehicle location which corresponds to therespective vehicle location data to the rallying location, the secondoutput is further configured to command the second-selected vehicle tosubsequently traverse from the rallying location to a destinationlocation which corresponds to the destination location data; communicatethe first output data to the first-selected vehicle, wherein, when thefirst output data is received at the first-selected vehicle, thefirst-selected vehicle will traverse from the vehicle location whichcorresponds to the respective vehicle location data to the user locationand the first-selected vehicle will subsequently traverse from the userlocation to the rallying location; and communicate the second outputdata to the second-selected vehicle, wherein, when the second outputdata is received at the second-selected vehicle, the second-selectedvehicle will traverse from the vehicle location which corresponds to therespective vehicle location data to the rallying location and thesecond-selected vehicle will subsequently traverse from the rallyinglocation to the destination location.
 2. The system of claim 1, whereinthe executable instructions further enable the controller to select therallying location based, at least in part, on the respective vehiclelocation data and respective system function data of the at least twoselected fleet vehicles.
 3. The system of claim 1, wherein each fleetvehicle in the plurality of fleet vehicles comprises a propulsion systemhaving at least one electric motor operatively connected to each of thevehicle wheels.
 4. The system of claim 3, wherein the second vehiclesystem is an on-board diagnostic feature and the system function datacomprises State of Charge information.
 5. The system of claim 1, whereineach fleet vehicle in the plurality of fleet vehicles comprises apropulsion system having at least one internal combustion engine.
 6. Thesystem of claim 4, wherein the second vehicle system is a fuel gauge andthe system function data comprises fuel-level information.
 7. The systemof claim 1, wherein: the mobile computing device is further configuredto generate time parameter data and is further configured to communicatethe time parameter data to the controller; and wherein the selection ofthe at least two fleet vehicles from the plurality of fleet vehicles isfurther based, at least in part, on the time parameter data.
 8. A methodto provide instructions to establish a vehicle chain, the methodcomprising: providing a memory configured to comprise one or moreexecutable instructions; providing a controller configured to executethe executable instructions, the controller further configured toreceive user location data and destination location data communicatedfrom a mobile computing device; providing a plurality of fleet vehicleseach of which is configured to communicate with the controller and eachof which comprises a first vehicle system, a second vehicle system, anda vehicle controls device, wherein the first vehicle system isconfigured to generate vehicle location data, wherein the second vehiclesystem is configured to generate system function data, and wherein thevehicle controls device is configured to command the fleet vehicle toautonomously complete one or more rideshare reservations; receiving, viathe controller, the user location data communicated from the mobilecomputing device; receiving, via the controller, the destinationlocation data communicated from the mobile computing device; receiving,via the controller, the respective vehicle location data communicatedfrom each fleet vehicle of the plurality of fleet vehicles; receiving,via the controller, the respective system function data communicatedfrom each fleet vehicle of the plurality of fleet vehicles; selecting,via the controller, at least two fleet vehicles from the plurality offleet vehicles, wherein each selection is based, at least in part, onthe vehicle location data and system function data of the respectivefleet vehicle in relation to the user location data, wherein the atleast two selected fleet vehicles are considered a first-selectedvehicle and a second-selected vehicle; producing, via the controller,first output data configured to instruct the vehicle controls device ofthe first-selected vehicle to command the first-selected vehicle totraverse from a vehicle location which corresponds to the respectivevehicle location data to a user location which corresponds to the userlocation data, the first output is further configured to command thefirst-selected vehicle to subsequently traverse from the user locationto a rallying location; producing, via the controller, second outputdata configured to instruct the vehicle controls device of thesecond-selected vehicle to command the second-selected vehicle totraverse from a vehicle location which corresponds to the respectivevehicle location data to the rallying location, the second output isfurther configured to command the second-selected vehicle tosubsequently traverse from the rallying location to a destinationlocation which corresponds to the destination location data;communicating, via the controller, the first output data to thefirst-selected vehicle, wherein, when the first output data is receivedat the first-selected vehicle, the first-selected vehicle will traversefrom the vehicle location which corresponds to the respective vehiclelocation data to the user location and the first-selected vehicle willsubsequently traverse from the user location to the rallying location;and communicating, via the controller, the second output data to thesecond-selected vehicle, wherein, when the second output data isreceived at the second-selected vehicle, the second-selected vehiclewill traverse from the vehicle location which corresponds to therespective vehicle location data to the rallying location and thesecond-selected vehicle will subsequently traverse from the rallyinglocation to the destination location.
 9. The method of claim 8, furthercomprising selecting, via the controller, the rallying location based,at least in part, on the respective vehicle location data and respectivesystem function data of the at least two selected fleet vehicles. 10.The method of claim 8, wherein each fleet vehicle in the plurality offleet vehicles comprises a propulsion system having at least oneelectric motor operatively connected to each of the vehicle wheels. 11.The method of claim 10, wherein the second vehicle system is an on-boarddiagnostic feature and the system function data comprises State ofCharge information.
 12. The method of claim 8, wherein each fleetvehicle in the plurality of fleet vehicles comprises a propulsion systemhaving at least one internal combustion engine.
 13. The method of claim12, wherein the second vehicle system is a fuel gauge and the systemfunction data comprises fuel-level information.
 14. The method of claim8, further comprising: wherein the mobile computing device is furtherconfigured to generate time parameter data and further configured tocommunicate the time parameter data to the controller; and wherein thestep of: selecting, via the controller, the at least two fleet vehiclesfrom the plurality of fleet vehicles is further based, at least in part,on the time parameter data.
 15. A non-transitory and machine-readablemedium having stored thereon executable instructions adapted to produceinstruction sets for at least two fleet vehicles such that the at leasttwo fleet vehicles establish a vehicle chain for the completion of arideshare reservation, which when provided to a controller and executedthereby, causes the controller to: receive user location datacommunicated from a mobile computing device; receive destinationlocation data communicated from the mobile computing device; receiverespective vehicle location data communicated from each fleet vehicle ofa plurality of fleet vehicles; receive respective system function datacommunicated from each fleet vehicle of the plurality of fleet vehicles;select at least two fleet vehicles from the plurality of fleet vehicles,wherein each selection is based, at least in part, on the vehiclelocation data and system function data of the respective fleet vehiclein relation to the user location data, wherein the at least two selectedfleet vehicles are considered a first-selected vehicle and asecond-selected vehicle; produce first output data configured toinstruct the vehicle controls device of the first-selected vehicle tocommand the first-selected vehicle to traverse from a vehicle locationwhich corresponds to the respective vehicle location data to a userlocation which corresponds to the user location data, the first outputis further configured to command the first-selected vehicle tosubsequently traverse from the user location to a rallying location;produce second output data configured to instruct the vehicle controlsdevice of the second-selected vehicle to command the second-selectedvehicle to traverse from a vehicle location which corresponds to therespective vehicle location data to the rallying location, the secondoutput is further configured to command the second-selected vehicle tosubsequently traverse from the rallying location to a destinationlocation which corresponds to the destination location data; communicatethe first output data to the first-selected vehicle, wherein, when thefirst output data is received at the first-selected vehicle, thefirst-selected vehicle will traverse from the vehicle location whichcorresponds to the respective vehicle location data to the user locationand the first-selected vehicle will subsequently traverse from the userlocation to the rallying location; and communicate the second outputdata to the second-selected vehicle, wherein, when the second outputdata is received at the second-selected vehicle, the second-selectedvehicle will traverse from the vehicle location which corresponds to therespective vehicle location data to the rallying location and thesecond-selected vehicle will subsequently traverse from the rallyinglocation to the destination location.
 16. The non-transitory andmachine-readable memory of claim 15, further comprises select therallying location based, at least in part, on the respective vehiclelocation data and respective system function data of the at least twoselected fleet vehicles.
 17. The non-transitory and machine-readablememory of claim 15, further comprises: receive time parameter datacommunicated from the mobile computing device; and wherein selection ofthe at least two fleet vehicles from the plurality of fleet vehicles isfurther based, at least in part, on the time parameter data.
 18. Thenon-transitory and machine-readable memory of claim 15, wherein eachfleet vehicle in the plurality of fleet vehicles comprises a propulsionsystem having at least one electric motor operatively connected to eachof the vehicle wheels.
 19. The non-transitory and machine-readablememory of claim 18, wherein the second vehicle system is an on-boarddiagnostic feature and the system function data comprises State ofCharge information.
 20. The non-transitory and machine-readable memoryof claim 15, wherein the second vehicle system is a fuel gauge and thesystem function data comprises fuel-level information.